Long term evolution intelligent subscriber profile

ABSTRACT

A network device may predict the use of a mobile device and configure a network based on the prediction. The network device may provide instructions to display coverage indicators for the mobile device based on the predictions.

TECHNICAL FIELD

The technical field generally relates to wireless communications andmore specifically relates to network resource provisioning.

BACKGROUND

Users are expecting data access anywhere for their mobile devices.Current wide are wireless networks, such as Global System for Mobilecommunications (GSM) and Long Term Evolution (LTE), allow internetservice providers to offer reasonable uplink and downlink bandwidth andspeed, in which customers can reach Internet based services. Forexample, cloud computing allows customers to make use of a wide range ofcloud based resources such as platform as a service (PaaS), storage as aservice (SaaS), computing as a service, and the like. But exponentialgrowth in cloud services and other Internet services has caused acorresponding increase in congestion on wide are wireless networks,which may reduce the effectiveness of cloud and other data services forusers.

WiFi and femtocell (femto) networks are widely available today and havethe potential to offer an alternative wide are wireless network domain.Yet, the authentication and authorization procedures of the alternativenetwork domain may make such opportunity cost and performanceprohibitive.

SUMMARY

The following presents a simplified summary that describes some aspectsand/or embodiments of the subject disclosure. This summary is not anextensive overview of the disclosure. Indeed, additional or alternativeaspects and/or embodiments of the subject disclosure may be availablebeyond those described in the summary.

In an example embodiment, a processor may access information associatedwith a mobile device, the information associated with the mobile devicemay comprise a first data usage for a first data session associated withthe mobile device. The data may be analyzed in a manner to predict asecond data usage for a second data session associated with the mobiledevice. Ultimately, a network for the mobile device may be configuredbased on the predicted second data usage for the second data sessionassociated with the mobile device.

In another example embodiment, a processor may be configured to accessmapping data for a route to a destination, as well as informationassociated with a mobile device, that comprises at least one of usagedata of the mobile device, a user profile associated with the mobiledevice, or demographic data associated with a user of the mobile device.Coverage may be predicted for the mobile device along the route based onan analysis of the information associated with the mobile device and themapping data for the route. The route to the destination may bedisplayed along with an indicator of the predicted coverage for themobile device along the route.

In another example embodiment, a system may comprise a network deviceand a mobile device, wherein the mobile device is capable of accessing awide area wireless network domain and alternate network domain. Thenetwork device may be configured to access historical informationassociated with the mobile device, access a current state of the widearea wireless network, and predict the use of the mobile device based onan analysis of the information associated with the mobile device and thecurrent state of the wide area wireless network. The mobile device maybe instructed to use the alternate domain network based on the predicteduse of the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description is better understood when read inconjunction with the appended drawings. For the purposes ofillustration, exemplary embodiments are shown in the drawings; however,the subject matter is not limited to the specific elements andinstrumentalities disclosed. In the drawings:

FIG. 1 is a system diagram of an example communications system in whichone or more disclosed embodiments may be implemented.

FIG. 2 is a block diagram of a non-limiting exemplary mobile device inwhich one or more disclosed embodiments may be implemented.

FIG. 3 is a block diagram of a non-limiting exemplary processor in whichone or more disclosed embodiments may be implemented.

FIG. 4 is a block diagram of a non-limiting exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichone or more disclosed embodiments may be implemented.

FIG. 5 illustrates a non-limiting exemplary architecture of a typicalGPRS network, segmented into four groups, in which one or more disclosedembodiments may be implemented.

FIG. 6 illustrates a non-limiting alternate block diagram of anexemplary GSM/GPRS/IP multimedia network architecture in which one ormore disclosed embodiments may be implemented.

FIG. 7 illustrates a Public Land Mobile Network (PLMN) block diagramview of an exemplary architecture in which one or more disclosedembodiments may be implemented.

FIG. 8 illustrates a non-limiting exemplary architecture of a LTEnetwork, in which one or more disclosed embodiments may be implemented.

FIG. 9 illustrates a non-limiting exemplary method 300 of implementingone or more disclosed embodiments.

FIG. 10 illustrates a non-limiting exemplary method 400 of implementingone or more disclosed embodiments.

FIG. 11 illustrates a non-limiting exemplary method 430 of implementingone or more disclosed embodiments.

FIG. 12 illustrates a non-limiting exemplary map that displays acoverage prediction.

FIG. 13 illustrates a non-limiting exemplary network configurationcomprising a wide area wireless network domain and an alternativenetwork domain.

FIG. 14 illustrates a non-limiting exemplary method for switchingbetween a wide area wireless network domain and an alternative networkdomain.

FIG. 15 illustrates a non-limiting exemplary network configuration 800according to one or more disclosed embodiments.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 1 is a diagram of an example communications system 100 in which oneor more disclosed embodiments may be implemented. The communicationssystem 100 may be a multiple access system that provides content, suchas voice, data, video, messaging, broadcast, etc., to multiple wirelessusers. The communications system 100 may enable multiple wireless usersto access such content through the sharing of system resources,including wireless bandwidth. For example, the communications systems100 may employ one or more channel access methods, such as code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrierFDMA (SC-FDMA), and the like. A communications system such as that shownin FIG. 1 may also be referred to herein as a network.

As shown in FIG. 1, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a radioaccess network (RAN) 104, a core network 106, a public switchedtelephone network (PSTN) 108, the Internet 110, and other networks 112,though it will be appreciated that the disclosed embodiments contemplateany number of WTRUs, base stations, networks, and/or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d may be any type of deviceconfigured to operate and/or communicate in a wireless environment. Byway of example, the WTRUs 102 a, 102 b, 102 c, 102 d may be configuredto transmit and/or receive wireless signals and may include userequipment (UE), a mobile station, a mobile device, a fixed or mobilesubscriber unit, a pager, a cellular telephone, a personal digitalassistant (PDA), a smartphone, a laptop, a netbook, a personal computer,a wireless sensor, consumer electronics, and the like.

The communications systems 100 may also include a base station 114 a anda base station 114 b. Each of the base stations 114 a, 114 b may be anytype of device configured to wirelessly interface with at least one ofthe WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to one or morecommunication networks, such as the core network 106, the Internet 110,and/or the networks 112. By way of example, the base stations 114 a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a HomeNode B, a Home eNode B, a site controller, an access point (AP), awireless router, and the like. While the base stations 114 a, 114 b areeach depicted as a single element, it will be appreciated that the basestations 114 a, 114 b may include any number of interconnected basestations and/or network elements.

The base station 114 a may be part of the RAN 104, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals within aparticular geographic region, which may be referred to as a cell (notshown). The cell may further be divided into cell sectors. For example,the cell associated with the base station 114 a may be divided intothree sectors. Thus, in an embodiment, the base station 114 a mayinclude three transceivers, i.e., one for each sector of the cell. Inanother embodiment, the base station 114 a may employ multiple-inputmultiple output (MIMO) technology and, therefore, may utilize multipletransceivers for each sector of the cell.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), visible light, etc.). Theair interface 116 may be established using any suitable radio accesstechnology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104 and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed DownlinkPacket Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114 a and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish the air interface116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.16 (i.e.,Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), InterimStandard 95 (IS-95), Interim Standard 856 (IS-856), Global System forMobile communications (GSM), Enhanced Data rates for GSM Evolution(EDGE), GSM EDGE (GERAN), and the like.

The base station 114 b in FIG. 1 may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, and the like. In oneembodiment, the base station 114 b and the WTRUs 102 c, 102 d mayimplement a radio technology such as IEEE 802.11 to establish a wirelesslocal area network (WLAN). In another embodiment, the base station 114 band the WTRUs 102 c, 102 d may implement a radio technology such as IEEE802.15 to establish a wireless personal area network (WPAN). In yetanother embodiment, the base station 114 b and the WTRUs 102 c, 102 dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 1,the base station 114 b may have a direct connection to the Internet 110.Thus, the base station 114 b may not be required to access the Internet110 via the core network 106.

The RAN 104 may be in communication with the core network 106, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. For example, the core network 106may provide call control, billing services, mobile location-basedservices, pre-paid calling, Internet connectivity, video distribution,etc., and/or perform high-level security functions, such as userauthentication. Although not shown in FIG. 1, it will be appreciatedthat the RAN 104 and/or the core network 106 may be in direct orindirect communication with other RANs that employ the same RAT as theRAN 104 or a different RAT. For example, in addition to being connectedto the RAN 104, which may be utilizing an E-UTRA radio technology, thecore network 106 may also be in communication with another RAN (notshown) employing a GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102 a,102 b, 102 c, 102 d to access the PSTN 108, the Internet 110, and/orother networks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) andthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired or wireless communications networks ownedand/or operated by other service providers. For example, the networks112 may include another core network connected to one or more RANs,which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities, i.e., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks. For example, the WTRU 102 c shown in FIG. 1 may be configured tocommunicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 2 illustrates an example wireless device 1010 (i.e., WTRU) that maybe used in connection with an embodiment. References will also be madeto other figures of the present disclosure as appropriate. For example,mobile devices 102 a, 102 b, and 102 c may be wireless devices of thetype described in regard to FIG. 2, and may have some, all, or none ofthe components and modules described in regard to FIG. 2. It will beappreciated that the components and modules of wireless device 1010illustrated in FIG. 2 are illustrative, and that any number and type ofcomponents and/or modules may be present in wireless device 1010. Inaddition, the functions performed by any or all of the components andmodules illustrated in FIG. 2 may be performed by any number of physicalcomponents. Thus, it is possible that in some embodiments thefunctionality of more than one component and/or module illustrated inFIG. 2 may be performed by any number or types of hardware and/orsoftware.

Processor 1021 may be any type of circuitry that performs operations onbehalf of wireless device 1010. Such circuitry may include circuitry andother components that enable processor 1021 to perform any of thefunctions and methods described herein. Such circuitry and othercomponents may also enable processor 1021 to communicate and/or interactwith other devices and components, for example any other component ofdevice of wireless device 1010, in such a manner as to enable processor118 and such other devices and/or components to perform any of thedisclosed functions and methods. In one embodiment, processor 1021executes software (i.e., computer readable instructions stored in acomputer readable medium) that may include functionality related todynamic network domain interoperability, for example. User interfacemodule 1022 may be any type or combination of hardware and/or softwarethat enables a user to operate and interact with wireless device 1010,and, in one embodiment, to interact with a system or software enablingthe user to place, request, and/or receive calls, text communications ofany type, voicemail, voicemail notifications, voicemail content and/ordata, and/or a system or software enabling the user to view, modify, ordelete related software objects. For example, user interface module 1022may include a display, physical and/or “soft” keys, voice recognitionsoftware, a microphone, a speaker and the like. Wireless communicationmodule 1023 may be any type of transceiver including any combination ofhardware and/or software that enables wireless device 1010 tocommunicate with wireless network equipment. Memory 1024 enableswireless device 1010 to store information, such as APNs, MNCs, MCCs,text communications content and associated data, multimedia content,software to efficiently process radio resource requests and servicerequests, and radio resource request processing preferences andconfigurations. Memory 1024 may take any form, such as internal randomaccess memory (RAM), an SD card, a microSD card and the like. Powersupply 1025 may be a battery or other type of power input (e.g., acharging cable that is connected to an electrical outlet, etc.) that iscapable of powering wireless device 1010. SIM 1026 may be any typeSubscriber Identity Module and may be configured on a removable ornon-removable SIM card that allows wireless device 1010 to store data onSIM 1026.

FIG. 3 is a block diagram of an example processor 1158 which may beemployed in any of the embodiments described herein, including as one ormore components of mobile devices 102 a thru 102 d, as one or morecomponents of network equipment such as S-GW 1343, PDN Gateway 1345 anyother component of networks 1340 and 1330, and/or any related equipment,and/or as one or more components of any third party system or subsystemthat may implement any portion of the subject matter described herein.It is emphasized that the block diagram depicted in FIG. 3 is exemplaryand not intended to imply a specific implementation. Thus, the processor1158 can be implemented in a single processor or multiple processors.Multiple processors can be distributed or centrally located. Multipleprocessors can communicate wirelessly, via hard wire, or a combinationthereof. Processor 1158 may include circuitry and other components thatenable processor 1158 to perform any of the functions and methodsdescribed herein. Such circuitry and other components may also enableprocessor 1158 to communicate and/or interact with other devices andcomponents, for example any other component of any device disclosedherein or any other device, in such a manner as to enable processor 1158and such other devices and/or components to perform any of the disclosedfunctions and methods.

As depicted in FIG. 3, the processor 1158 comprises a processing portion1160, a memory portion 1162, and an input/output portion 1164. Theprocessing portion 1160, memory portion 1162, and input/output portion1164 are coupled together (coupling not shown in FIG. 3) to allowcommunications between these portions. The input/output portion 1164 iscapable of providing and/or receiving components, commands, and/orinstructions, utilized to, for example, request and receive APNs, MNCs,and/or MCCs, establish and terminate communications sessions, transmitand receive service requests and data access request data and responses,transmit, receive, store and process text, data, and voicecommunications, execute software that efficiently processes radioresource requests, receive and store service requests and radio resourcerequests, radio resource request processing preferences andconfigurations, and/or perform any other function described herein.

The processor 1158 may be implemented as a client processor and/or aserver processor. In a basic configuration, the processor 1158 mayinclude at least one processing portion 1160 and memory portion 1162.The memory portion 1162 can store any information utilized inconjunction with establishing, transmitting, receiving, and/orprocessing text, data, and/or voice communications,communications-related data and/or content, voice calls, othertelephonic communications, etc. For example, the memory portion iscapable of storing APNs, MNCs, MCCs, service requests, radio resourcerequests, QoS and/or APN parameters, software for dynamic network domaininteroperability, intelligent subscriber profiles, text and datacommunications, calls, voicemail, multimedia content, visual voicemailapplications, etc. Depending upon the exact configuration and type ofprocessor, the memory portion 1162 can be volatile (such as RAM) 1166,non-volatile (such as ROM, flash memory, etc.) 1168, or a combinationthereof. The processor 1158 can have additional features/functionality.For example, the processor 1158 may include additional storage(removable storage 1170 and/or non-removable storage 1172) including,but not limited to, magnetic or optical disks, tape, flash, smart cardsor a combination thereof. Computer storage media, such as memory andstorage elements 1162, 1170, 1172, 1166, and 1168, may include volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules, or other data.Computer storage media include, but are not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,universal serial bus (USB) compatible memory, smart cards, or any othermedium that can be used to store the desired information and that can beaccessed by the processor 1158. Any such computer storage media may bepart of the processor 1158. As described herein, a computer storagemedia is an article of manufacture and thus not a transient signal.

The processor 1158 may also contain the communications connection(s)1180 that allow the processor 1158 to communicate with other devices,for example through a radio access network (RAN). Communicationsconnection(s) 1180 is an example of communication media. Communicationmedia typically embody computer-readable instructions, data structures,program modules or other data in a modulated data signal such as acarrier wave or other transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection as might be used with a land line telephone, andwireless media such as acoustic, RF, infrared, cellular, and otherwireless media. The term computer-readable media as used herein includesboth storage media and communication media. The processor 1158 also canhave input device(s) 1176 such as keyboard, keypad, mouse, pen, voiceinput device, touch input device, etc. Output device(s) 1174 such as adisplay, speakers, printer, etc. also can be included.

A RAN as described herein may comprise any telephony radio network, orany other type of communications network, wireline or wireless, or anycombination thereof. The following description sets forth some exemplarytelephony radio networks, such as the global system for mobilecommunications (GSM), and non-limiting operating environments. Theoperating environments described herein should be considerednon-exhaustive, however, and the network architectures merely show howdisclosed subject matter (e.g., dynamic network domain interoperability)may be implemented with stationary and non-stationary network structuresand architectures. It can be appreciated, however, that disclosedsubject matter as described herein may be incorporated with existingand/or future alternative architectures for communication networks aswell.

GSM is one of the most widely utilized wireless access systems intoday's fast growing communication environment. GSM providescircuit-switched data services to subscribers, such as mobile telephoneor computer users. The General Packet Radio Service (GPRS), which is anextension to GSM technology, introduces packet switching to GSMnetworks. The GPRS uses a packet-based wireless communication technologyto transfer high and low speed data and signaling in an efficientmanner. The GPRS attempts to optimize the use of network and radioresources, thus enabling the cost effective and efficient use of GSMnetwork resources for packet mode applications.

The exemplary GSM/GPRS environment and services described herein alsomay be extended to 3G services, such as Universal Mobile TelephoneSystem (UMTS), Frequency Division Duplexing (FDD) and Time DivisionDuplexing (TDD), High Speed Packet Data Access (HSPDA), cdma2000 1xEvolution Data Optimized (EVDO), Code Division Multiple Access-2000(cdma2000 3x), Time Division Synchronous Code Division Multiple Access(TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), EnhancedData GSM Environment (EDGE), International MobileTelecommunications-2000 (IMT-2000), Digital Enhanced CordlessTelecommunications (DECT), 4G Services such as Long Term Evolution(LTE), etc., as well as to other network services that become availablein time. In this regard, the disclosed subject matter (e.g., dynamicnetwork domain interoperability) may be applied independently of themethod of data transport and does not depend on any particular networkarchitecture or underlying protocols.

FIG. 4 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichthe disclosed subject matter (e.g., dynamic network domaininteroperability) may be practiced. In an example configuration, any RANas described herein may be encompassed by or interact with the networkenvironment depicted in FIG. 4. Similarly, mobile devices 102 a, 102 b,and 102 c may communicate or interact with a network environment such asthat depicted in FIG. 4. In such an environment, there may be aplurality of Base Station Subsystems (BSS) 900 (only one is shown), eachof which comprises a Base Station Controller (BSC) 902 serving aplurality of Base Transceiver Stations (BTS) such as BTSs 904, 906, and908. BTSs 904, 906, 908, etc. are the access points where users ofpacket-based mobile devices (e.g., mobile devices 102 a, 102 b, and 102c) become connected to the wireless network. In exemplary fashion, thepacket traffic originating from user devices (e.g., mobile devices 102a, 102 b, and 102 c) may be transported via an over-the-air interface toa BTS 908, and from the BTS 908 to the BSC 902. Base station subsystems,such as BSS 900, may be a part of internal frame relay network 910 thatcan include Service GPRS Support Nodes (SGSN) such as SGSN 912 and 914.Each SGSN may be connected to an internal packet network 920 throughwhich a SGSN 912, 914, etc. may route data packets to and from aplurality of gateway GPRS support nodes (GGSN) 922, 924, 926, etc. Asillustrated, SGSN 914 and GGSNs 922, 924, and 926 may be part ofinternal packet network 920. Gateway GPRS serving nodes 922, 924 and 926may provide an interface to external Internet Protocol (IP) networks,such as Public Land Mobile Network (PLMN) 950, corporate intranets 940,or Fixed-End System (FES) or the public Internet 930. As illustrated,subscriber corporate network 940 may be connected to GGSN 924 viafirewall 932, and PLMN 950 may be connected to GGSN 924 via bordergateway router 934. The Remote Authentication Dial-In User Service(RADIUS) server 942 may be used for caller authentication when a user ofa mobile cellular device calls corporate network 940.

Generally, there can be four different cell sizes in a GSM network,referred to as macro, micro, pico, and umbrella cells. The coverage areaof each cell is different in different environments. Macro cells may beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells may betypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells may be used mainly indoors.On the other hand, umbrella cells may be used to cover shadowed regionsof smaller cells and fill in gaps in coverage between those cells.

FIG. 5 illustrates an architecture of a typical GPRS network segmentedinto four groups: users 1050, radio access network 1060, core network1070, and interconnect network 1080. Users 1050 may comprise a pluralityof end users (though only mobile subscriber 1055 is shown in FIG. 5). Inan example embodiment, the device depicted as mobile subscriber 1055 maycomprise any of mobile devices 102 a, 102 b, and 102 c. Radio accessnetwork 1060 comprises a plurality of base station subsystems such asBSSs 1062, which include BTSs 1064 and BSCs 1066. Core network 1070comprises a host of various network elements. As illustrated here, corenetwork 1070 may comprise Mobile Switching Center (MSC) 1071, ServiceControl Point (SCP) 1072, gateway MSC 1073, SGSN 1076, Home LocationRegister (HLR) 1074, Authentication Center (AuC) 1075, Domain NameServer (DNS) 1077, and GGSN 1078. Interconnect network 1080 may alsocomprise a host of various networks and other network elements. Asillustrated in FIG. 5, interconnect network 1080 comprises PublicSwitched Telephone Network (PSTN) 1082, Fixed-End System (FES) orInternet 1084, firewall 1088, and Corporate Network 1089.

A mobile switching center may be connected to a large number of basestation controllers. At MSC 1071, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (PSTN) 1082 through Gateway MSC (GMSC)1073, and/or data may be sent to SGSN 1076 that may send the datatraffic to GGSN 1078 for further forwarding.

When MSC 1071 receives call traffic, for example, from BSC 1066, it maysend a query to a database hosted by SCP 1072. The SCP 1072 may processthe request and may issue a response to MSC 1071 so that it may continuecall processing as appropriate.

The HLR 1074 may be a centralized database for users to register to theGPRS network. In some embodiments, HLR 1074 may be a device such asHSSs. HLR 1074 may store static information about the subscribers suchas the International Mobile Subscriber Identity (IMSI), APN profiles asdescribed herein, subscribed services, and a key for authenticating thesubscriber. HLR 1074 may also store dynamic subscriber information suchas dynamic APN profiles and the current location of the mobilesubscriber. HLR 1074 may also serve to intercept and determine thevalidity of destination numbers in messages sent from a device, such asmobile subscriber 1055, as described herein. Associated with HLR 1074may be AuC 1075. AuC 1075 may be a database that contains the algorithmsfor authenticating subscribers and may include the associated keys forencryption to safeguard the user input for authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as mobile devices 102 a, 102 b, and 102 c, used by an enduser of a mobile cellular service or a wireless provider. When a mobilesubscriber turns on his or her mobile device, the mobile device may gothrough an attach process by which the mobile device attaches to an SGSNof the GPRS network. In FIG. 5, when mobile subscriber 1055 initiatesthe attach process by turning on the network capabilities of the mobiledevice, an attach request may be sent by mobile subscriber 1055 to SGSN1076. The SGSN 1076 queries another SGSN, to which mobile subscriber1055 was attached before, for the identity of mobile subscriber 1055.Upon receiving the identity of mobile subscriber 1055 from the otherSGSN, SGSN 1076 may request more information from mobile subscriber1055. This information may be used to authenticate mobile subscriber1055 to SGSN 1076 by HLR 1074. Once verified, SGSN 1076 sends a locationupdate to HLR 1074 indicating the change of location to a new SGSN, inthis case SGSN 1076. HLR 1074 may notify the old SGSN, to which mobilesubscriber 1055 was attached before, to cancel the location process formobile subscriber 1055. HLR 1074 may then notify SGSN 1076 that thelocation update has been performed. At this time, SGSN 1076 sends anAttach Accept message to mobile subscriber 1055, which in turn sends anAttach Complete message to SGSN 1076.

After attaching itself to the network, mobile subscriber 1055 may thengo through the authentication process. In the authentication process,SGSN 1076 may send the authentication information to HLR 1074, which maysend information back to SGSN 1076 based on the user profile that waspart of the user's initial setup. The SGSN 1076 may then send a requestfor authentication and ciphering to mobile subscriber 1055. The mobilesubscriber 1055 may use an algorithm to send the user identification(ID) and password to SGSN 1076. The SGSN 1076 may use the same algorithmand compares the result. If a match occurs, SGSN 1076 authenticatesmobile subscriber 1055.

Next, the mobile subscriber 1055 may establish a user session with thedestination network, corporate network 1089, by going through a PacketData Protocol (PDP) activation process. Briefly, in the process, mobilesubscriber 1055 may request access to an Access Point Name (APN), forexample, UPS.com, and SGSN 1076 may receive the activation request frommobile subscriber 1055. SGSN 1076 may then initiate a Domain NameService (DNS) query to learn which GGSN node has access to the UPS.comAPN. The DNS query may be sent to the DNS server within the core network1070, such as DNS 1077, that may be provisioned to map to one or moreGGSN nodes in the core network 1070. Based on the APN, the mapped GGSN1078 may access the requested corporate network 1089. The SGSN 1076 maythen send to GGSN 1078 a Create Packet Data Protocol (PDP) ContextRequest message that contains necessary information. The GGSN 1078 maysend a Create PDP Context Response message to SGSN 1076, which may thensend an Activate PDP Context Accept message to mobile subscriber 1055.

Once activated, data packets of the call made by mobile subscriber 1055may then go through radio access network 1060, core network 1070, andinterconnect network 1080, in a particular fixed-end system, or Internet1084 and firewall 1088, to reach corporate network 1089.

Thus, network elements that can invoke the functionality of dynamicnetwork domain interoperability systems and methods and other subjectmatter described herein may include, but are not limited to, GatewayGPRS Support Node tables, Fixed End System router tables, firewallsystems, VPN tunnels, and any number of other network elements asrequired by the particular digital network.

FIG. 6 illustrates another exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture 1100 in which the dynamic network domaininteroperability systems and methods and other subject matter describedherein may be incorporated. As illustrated, architecture 1100 of FIG. 6includes a GSM core network 1101, a GPRS network 1130 and an IPmultimedia network 1138. The GSM core network 1101 includes a MobileStation (MS) 1102, at least one Base Transceiver Station (BTS) 1104 anda Base Station Controller (BSC) 1106. The MS 1102 is physical equipmentor Mobile Equipment (ME), such as a mobile telephone or a laptopcomputer (e.g., mobile devices 102 a, 102 b, and 102 c) that is used bymobile subscribers, in one embodiment with a Subscriber identity Module(SIM). The SIM includes an International Mobile Subscriber Identity(IMSI), which is a unique identifier of a subscriber. The SIM may alsoinclude APNs. The BTS 1104 may be physical equipment, such as a radiotower, that enables a radio interface to communicate with the MS. EachBTS may serve more than one MS. The BSC 1106 may manage radio resources,including the BTS. The BSC may be connected to several BTSs. The BSC andBTS components, in combination, are generally referred to as a basestation (BSS) or radio access network (RAN) 1103.

The GSM core network 1101 may also include a Mobile Switching Center(MSC) 1108, a Gateway Mobile Switching Center (GMSC) 1110, a HomeLocation Register (HLR) 1112, Visitor Location Register (VLR) 1114, anAuthentication Center (AuC) 1118, and an Equipment Identity Register(EIR) 1116. The MSC 1108 may perform a switching function for thenetwork. The MSC may also perform other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1110 may provide a gateway between the GSM network and other networks,such as an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1120. Thus, the GMSC 1110 providesinterworking functionality with external networks.

The HLR 1112 may be a database that may contain administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. Such information may include APNs and APN profiles. The HLR1112 may also contain the current location of each MS. The VLR 1114 maybe a database that contains selected administrative information from theHLR 1112. The VLR may contain information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1112 and the VLR 1114,together with the MSC 1108, may provide the call routing and roamingcapabilities of GSM. The AuC 1116 may provide the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1118 may storesecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1109 allows one-to-one shortmessage service (SMS), or multimedia message service (MMS), messages tobe sent to/from the MS 1102. A Push Proxy Gateway (PPG) 1111 is used to“push” (i.e., send without a synchronous request) content to the MS1102. The PPG 1111 acts as a proxy between wired and wireless networksto facilitate pushing of data to the MS 1102. A Short Message Peer toPeer (SMPP) protocol router 1113 may be provided to convert SMS-basedSMPP messages to cell broadcast messages. SMPP is a protocol forexchanging SMS messages between SMS peer entities such as short messageservice centers. The SMPP protocol is often used to allow third parties,e.g., content suppliers such as news organizations, to submit bulkmessages.

To gain access to GSM services, such as voice, data, short messageservice (SMS), and multimedia message service (MMS), the MS may firstregister with the network to indicate its current location by performinga location update and IMSI attach procedure. MS 1102 may send a locationupdate including its current location information to the MSC/VLR, viaBTS 1104 and BSC 1106. The location information may then be sent to theMS's HLR. The HLR may be updated with the location information receivedfrom the MSC/VLR. The location update may also be performed when the MSmoves to a new location area. Typically, the location update may beperiodically performed to update the database as location updatingevents occur.

GPRS network 1130 may be logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1132, a cell broadcast and a GatewayGPRS support node (GGSN) 1134. The SGSN 1132 may be at the samehierarchical level as the MSC 1108 in the GSM network. The SGSN maycontrol the connection between the GPRS network and the MS 1102. TheSGSN may also keep track of individual MS's locations and securityfunctions and access controls.

Cell Broadcast Center (CBC) 1133 may communicate cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile telephone customers whoare located within a given part of its network coverage area at the timethe message is broadcast.

GGSN 1134 may provide a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1136. That is, the GGSN mayprovide interworking functionality with external networks, and set up alogical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it may be transferred to an external TCP-IPnetwork 1136, such as an X.25 network or the Internet. In order toaccess GPRS services, the MS first attaches itself to the GPRS networkby performing an attach procedure. The MS then activates a packet dataprotocol (PDP) context, thus activating a packet communication sessionbetween the MS, the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services may be used inparallel. The MS may operate in one three classes: class A, class B, andclass C. A class A MS may attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS may also supportsimultaneous operation of GPRS services and GSM services. For example,class A mobiles may receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS may attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

GPRS network 1130 may be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS networkmay be indicated by a parameter in system information messagestransmitted within a cell. The system information messages may direct anMS where to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS may receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS maysuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS may bereceiving data and may not be listening to a paging channel. In a NOM3network, a MS may monitor pages for a circuit switched network whilereceiving data and vice versa.

The IP multimedia network 1138 was introduced with 3GPP Release 5, andmay include IP multimedia subsystem (IMS) 1140 to provide richmultimedia services to end users. A representative set of the networkentities within IMS 1140 are a call/session control function (CSCF), amedia gateway control function (MGCF) 1146, a media gateway (MGW) 1148,and a master subscriber database, called a home subscriber server (HSS)1150. HSS 1150 may be common to GSM core network 1101, GPRS network 1130as well as IP multimedia network 1138. HSS 1150 may include multipleHSSs.

IP multimedia system 1140 may be built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1143, a proxy CSCF (P-CSCF) 1142, and a serving CSCF (S-CSCF) 1144. TheP-CSCF 1142 is the MS's first point of contact with the IMS 1140. TheP-CSCF 1142 may forward session initiation protocol (SIP) messagesreceived from the MS to an SIP server in a home network (and vice versa)of the MS. The P-CSCF 1142 may also modify an outgoing request accordingto a set of rules defined by the network operator (for example, addressanalysis and potential modification).

I-CSCF 1143 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. I-CSCF 1143 may contact subscriberlocation function (SLF) 1145 to determine which HSS 1150 to use for theparticular subscriber, if multiple HSSs 1150 are present. S-CSCF 1144may perform the session control services for MS 1102. This includesrouting originating sessions to external networks and routingterminating sessions to visited networks. S-CSCF 1144 may also decidewhether an application server (AS) 1152 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision may be based on information receivedfrom HSS 1150 (or other sources, such as application server 1152). AS1152 may also communicate to location server 1156 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of MS 1102.

HSS 1150 may contain a subscriber profile and keep track of which corenetwork node is currently handling the subscriber. It may also supportsubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1150, a subscriber location function providesinformation on the HSS 1150 that contains the profile of a givensubscriber.

MGCF 1146 may provide interworking functionality between SIP sessioncontrol signaling from the IMS 1140 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown.) It may also control themedia gateway (MGW) 1148 that provides user-plane interworkingfunctionality (e.g., converting between AMR- and PCM-coded voice.) MGW1148 may also communicate with other IP multimedia networks 1154.

Push to Talk over Cellular (PoC) capable mobile telephones may registerwith the wireless network when the telephones are in a predefined area(e.g., job site, etc.) When the mobile telephones leave the area, theymay register with the network in their new location as being outside thepredefined area. This registration, however, does not indicate theactual physical location of the mobile telephones outside thepre-defined area.

FIG. 7 illustrates a PLMN block diagram view of an exemplaryarchitecture in which dynamic network domain interoperability systemsand methods and other subject matter described herein may beincorporated. Mobile Station (MS) 1301 is the physical equipment used bythe PLMN subscriber. In one illustrative embodiment, communicationsdevice 40 may serve as Mobile Station 1301. Mobile Station 1301 may beone of, but not limited to, a cellular telephone, a cellular telephonein combination with another electronic device or any other wirelessmobile communication device.

Mobile Station 1301 may communicate wirelessly with Base Station System(BSS) 1310. BSS 1310 contains a Base Station Controller (BSC) 1311 and aBase Transceiver Station (BTS) 1312. BSS 1310 may include a single BSC1311/BTS 1312 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1310 is responsible for communicating withMobile Station 1301 and may support one or more cells. BSS 1310 isresponsible for handling cellular traffic and signaling between MobileStation 1301 and Core Network 1340. Typically, BSS 1310 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1301 may communicate wirelessly with RadioNetwork System (RNS) 1320. RNS 1320 contains a Radio Network Controller(RNC) 1321 and one or more Node(s) B 1322. RNS 1320 may support one ormore cells. RNS 1320 may also include one or more RNC 1321/Node B 1322pairs or alternatively a single RNC 1321 may manage multiple Nodes B1322. RNS 1320 is responsible for communicating with Mobile Station 1301in its geographically defined area. RNC 1321 is responsible forcontrolling the Node(s) B 1322 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1321 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1301's access to the Core Network (CN) 1340.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1330 is aradio access network that provides wireless data communications forMobile Station 1301 and User Equipment 1302. E-UTRAN 1330 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1330 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1331 and E-UTRAN Node B (eNB) 1332. E-UTRAN 1330 may contain oneor more eNBs. User Equipment 1302 may be any user device capable ofconnecting to E-UTRAN 1330 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1330. The improvedperformance of the E-UTRAN 1330 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 7 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 9-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1301 may communicate with any or all of BSS1310, RNS 1320, or E-UTRAN 1330. In a illustrative system, each of BSS1310, RNS 1320, and E-UTRAN 1330 may provide Mobile Station 1301 withaccess to Core Network 1340. The Core Network 1340 may include of aseries of devices that route data and communications between end users.Core Network 1340 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched-Media Gateway Function (CS-MGW) 1341 is part ofCore Network 1340, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1360 and Gateway MSCServer 1361 in order to facilitate Core Network 1340 resource control inthe CS domain. Functions of CS-MGW 1341 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1340 mayreceive connections to Mobile Station 1301 through BSS 1310, RNS 1320 orboth.

Serving GPRS Support Node (SGSN) 1342 stores subscriber data regardingMobile Station 1301 in order to facilitate network functionality. SGSN1342 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1342 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1344 address for each GGSN where an active PDPexists. GGSN 1344 may implement a location register function to storesubscriber data it receives from SGSN 1342 such as subscription orlocation information.

Serving Gateway (S-GW) 1343 is an interface which provides connectivitybetween E-UTRAN 1330 and Core Network 1340. Functions of S-GW 1343include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1350, and mobility anchoring forinter-network mobility. PCRF 1350 uses information gathered from S-GW1343, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1345 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1363 is a database for user information,and stores subscription data regarding Mobile Station 1301 or UserEquipment 1302 for handling calls or data sessions. Networks may containone HSS 1363 or more if additional resources are required. Exemplarydata stored by HSS 1363 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 1363 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 1360 provides user location functionality. WhenMobile Station 1301 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1360, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1301 registration orprocedures for handover of Mobile Station 1301 to a different section ofthe Core Network 1340. GMSC Server 1361 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1362 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1301. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1301 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1362, preventing its use on the network. Mobility ManagementEntity (MME) 1364 is a control node which may track Mobile Station 1301or User Equipment 1302 if the devices are idle. Additional functionalitymay include the ability of MME 1364 to contact an idle Mobile Station1301 or User Equipment 1302 if retransmission of a previous session isrequired.

FIG. 8 illustrates a non-limiting exemplary architecture of a LTEnetwork, in which one or more disclosed embodiments may be implemented.As illustrated, network architecture 200 of FIG. 8 includes an EvolvedUniversal Terrestrial Radio Access Network (EUTRAN) 205, a MME 210, aSGW 215, an intelligent HSS 218, a PCRF 240, and a PDN gateway/Policyand Charging Enforcement Function (PCEF) 242. The PDN gateway 242 mayprovide a gateway between the LTE network and a public packet datanetwork 246 which may comprise IP networks that connect to a cloudservice or other data services. The different types of cloud servicesmay include Infrastructure as a service (IaaS), Platform as a service(PaaS), Software as a service (SaaS), Storage as a service (STaaS),Security as a service (SECaaS), Data as a service (DaaS), Testenvironment as a service (TEaaS), Desktop as a service (DaaS), orapplication programming interface (API) as a service (APIaaS).

Intelligent HSS (iHSS) 218 may perform functions customary to an HSSsuch as AAA functions and subscriber location functions. In addition,intelligent HSS 218 may comprise an action and promotion engine 236, apolicy engine 233, an analysis and prediction engine 230, and anintelligent subscriber profile 238. In an embodiment, intelligent HSS218 may also have data usage 220 for cloud services, user profile data223, and rate plan data 226. Data usage 220 for cloud services maycomprise information such as the time of day a particular type of cloudservice was accessed, duration of cloud service access, volume of cloudservice data accessed, provider of the cloud service, and the like. UserProfile Data 223 may comprise general user preference data (e.g., phonemodel), wireless technology format capability (e.g., GPRS, LTE, WiFi,CDMA, etc), user preferences for cloud services (e.g., preferred QoS fora cloud service), applications associated with the mobile device (e.g.,social media application, cloud service application, radio application,music application, etc), and common demographics of a user of a WTRU203. The demographics may include user age, home ownership, employmentstatus, gender, height, weight, birthday, college education status,income, and the like. Rate Plan Data 226 may comprise rate planinformation such as whether the rate plan is time based, bulk data usagebased, pay per use based, and the like.

One or more of the engines in the iHSS may use data usage 220, userprofile data 223, and rate plan data 226. All engines may communicateinstructions to PCRF 240 real-time as well as placing instructions andother information in the intelligent subscriber profile 238. ThePrediction engine 230 may analyze data usage 220, user profile data 223,and rate plan data 226 to predict future behavior. The Policy andCharging Engine 230 may enforce quality of service (QoS) and charging todeliver superior user experience. The Action and Promotion Engine 236may leverage coupon and campaign to promote usage of LTE cloud computingresources. The intelligent subscriber profile 238 may be similar to auser profile, but include the resulting analysis of the Action andPromotion Engine 236, Policy and Charging Engine 233, and Analysis andPrediction Engine 230. For example, the intelligent subscriber profile238 may comprise time delineated forecasts (predictions) of usagepatterns, recommended promotions and campaigns, time delineated networkconfiguration for a connected WTRU, and the like.

FIG. 9 illustrates a non-limiting exemplary method 300 of implementingone or more disclosed embodiments. In an exemplary embodiment at block305, a MME may query an iHSS for mobility management (e.g., authenticatea user identity). At block 310, the iHSS may query the MME for usagedata and rate plan for the subscriber cloud service session. At block315, the iHSS may perform analysis and prediction of future behaviorbased on past history of the user. At block 320, the iHSS may requestthe PCRF to retrieve policy and charging rules for the user. At block325, the iHSS may perform promotion and campaign based on informationgathered about the user data usage, user profile, rate plan, and thelike. Performing promotion and campaign may include the iHSScommunicating information that may encourage the user to expand theservice mix of the user. An example service suggestion may be thepurchase of a data plan that includes a provisioned (i.e., configured)tunnel to the cloud service network that allows the user a guaranteedend-to-end bandwidth.

The iHSS may perform real-time analysis (e.g., analysis during a cloudservice session) so that intelligent subscriber profile information maybe updated to the iHSS for future cloud services for the originatinguser device and the terminating cloud service device. A wide range ofLTE network elements (e.g., MME, PCRF, PDN-GW, PCEF, etc) may query theiHSS for intelligent subscriber profile information and be configuredbased on the intelligent subscriber profile. Interaction between LTEnetwork elements (e.g., MME, PCEF, PCRF, etc) and iHSS may occur priorto, during, and/or after the cloud service session.

FIG. 10 illustrates a non-limiting exemplary method 400 of implementingone or more disclosed embodiments. In an embodiment, at block 405 theiHSS may analyze several WTRU cloud service sessions data pointsgathered over a period of time. After analyzing the aforementioned cloudservice sessions the iHSS may determine (i.e., predict) at block 410 thewireless resources (e.g., type and amount of wireless access) and othernetwork resources (e.g., backbone network bandwidth and access to awireless network) that would be best tailored to the WTRU cloud servicesession. Network resources may include number of wireless channelsallocated, type of wireless technology (e.g., WiFi, GPRS, femtocell,LTE), amount of bandwidth, quality of service, network path, core orbackbone network devices (wireless and wirleine) as described herein,and the like. At block 415, the iHSS may decide when the aforementioneddetermined resources should be allocated. For example, the resources maybe allocated immediately upon powering on the device, upon wake-up ofthe device after wireless inactivity or device inactivity, or during thecloud service session (e.g., throttling up or down of reserved bandwidthduring the cloud service session).

The iHSS may analyze several different data points associated with theWTRU cloud service sessions such as the time of day for cloud servicesessions and access to a particular cloud service. In another example,the user may be transitioned to a cell (e.g., wireless tower) earlierthan normal based on historical WTRU information which was constructedinto a probable (i.e., predicted) travel route for the WTRU. Thepredicted cell handover route may be pre-constructed by the Analysis andPrediction Engine of the iHSS and recorded within the intelligentsubscriber profile. In an embodiment, the cloud service provider mayhave an agreement with the wide are wireless network provider toconfigure the mobile phone customer device in a particular manner whenaccessing the cloud service provider's cloud services. Network access(including wireless access) may be configured based on the type of cloudservice accessed.

The iHSS may collaborate with LTE network elements (e.g., MME, PCRF,PDN-GW, etc) to provide promotion and incentives for usage of cloudservice resources. FIG. 11 illustrates a non-limiting exemplary method430 of implementing one or more disclosed embodiments. In an embodiment,as shown in method 430, at block 435 the iHSS may analyze several WTRUcloud service sessions. At block 440, after analyzing the aforementionedcloud service sessions the iHSS may determine data usage plans or otherservices that may be of interest to the WTRU user and record it into theintelligent subscriber profile associated with the WTRU. At block 445,the iHSS may determine when the aforementioned determined servicepromotions should be displayed and record it into the intelligentsubscriber profile associated with the WTRU. For example, the resourcesmay be displayed upon powering on the WTRU, upon wake-up of the WTRUafter wireless inactivity, or during the cloud service session. In anembodiment, aspects of the network may be pre-provisioned inanticipation of use by the WTRU user at a particular time. For example,the type of QoS may be pre-provisioned for a particular time frame thata WTRU of a user may access cloud services. In an embodiment, based ondata analysis as disclosed herein, an advertised paid service (e.g.,data usage plan) may be selected immediately for a limited amount oftime (e.g., only for the duration of a cloud service session). If thepaid service is selected, the policy and charging engine may adjust theintelligent subscriber profile accordingly and the profile change may becommunicated to the necessary network elements. In another embodiment,based on data analysis as disclosed herein, there may be anadvertisement or promotion for a cloud service. The cloud servicepromotion may be for a competitor cloud service with a lower price andcomparable cloud services, for example.

It may be beneficial for the iHSS to handle the predictive analysis,intelligent subscriber profile changes, and different engines disclosedherein because the iHSS is one of the first network devices in thewireless network that may already be configured to assist inprovisioning of a user device to connect to the wireless network. TheiHSS allows for the upfront provisioning of appropriate resources upon adevice's initial connection with the network. Intelligent HSSfunctionalities may also be housed in an HLR type device. Although cloudservices are discussed, many of the disclosed concepts may be applied toother Internet, voice, or data network services. At least a portion ofthe intelligent subscriber profile created by the iHSS may becommunicated to other network devices such as the MME, SGW, PDN-GW,PCRF, PCEF, or the like for implementation. The iHSS may analyze aparticular device linked to a user or a group of devices that may berelated to a common user account. The intelligent subscriber profile maybe used to enhance cloud computing sessions. The intelligent subscriberprofile may be automatically updated based on real time analysis. Theanalysis, gathering of data, and the like as disclosed herein may applyto a WTRU associated with a particular user account. So it iscontemplated that a WTRU may be used for the first time, but anintelligent subscriber profile may be apply to the WTRU because of itsassociation with a subscriber.

The intelligent subscriber profile and the other functions of the iHSSmay be used in conjunction with navigation systems. As disclosed herein,the iHSS may analyze a user device usage pattern of a cloud service,Internet, or more generally data services. The iHSS may then predict anetwork configuration that is tailored to a WTRU or a WTRU associatedwith a subscriber account in a way that can be displayed to a device ona navigation map corresponding to text directions. The directions may bebased on walking, driving, or other modes of transportation.

As shown in FIG. 12, in an embodiment, User X with device WTRU X andUser Y with device WTRU Y may intend to travel at the same time and inthe same vehicle from Point A 505 to Point B 510 as show on highway map500. User X may enter a request for directions from Point A 505 to PointB 510 on WTRU X or a device communicatively connected the WTRU X (e.g.,a vehicle navigation system). User Y may also enter a request fordirections from Point A 505 to Point B 510. In an embodiment, therequest for directions of one or more devices may be centralized. Forexample, the vehicle navigation system may be communicatively connectedto both WTRU Y and WTRU X which may allow for the access of thenecessary data to perform the necessary operations. The generalnavigation information may also comprise WTRU coverage information thatmay be based on analysis done by the iHSS (e.g., Analysis and PredictionEngine and/or intelligent subscriber profile).

As shown on highway map 500, there may be multiple routes from Point A505 to Point B 510 such as Route 515 and a Route 520. As shown in block530, the same mileage and time may be computed for WTRU X and WTRU Y,but different predicted coverages may be computed based on therespective devices intelligent subscriber profile. The predictedcoverage may be an indicator of (or based on) one or more of thefollowing: download/upload speeds, actual wireless antenna coverage,network congestion, network outages, network infrastructure (e.g., GSMor WiFi), and the like. The predicted coverage may also take intoaccount the predicted speed of the WTRU (e.g., vehicle traffic orwalking) to determine coverage scenarios.

As shown in block 530 for Route 515, WTRU X has a predicted coverage of90% for the entirety of the route 515 while WTRU Y has a predictedcoverage of 61%. Block 535 for Route 520 displays a predicted coverageof 86% for WTRU X and a predicted coverage of 81% for WTRU Y. Due to theimportance of network access for entertainment (e.g., downloading highdefinition movies) or work purposes (e.g., accessing cloud services forwork) route 520 which has a longer duration of 30 minutes, but has morestable predicted coverage, may be chosen over route 515 which has ashorter duration of 22 minutes. In an embodiment, there may be colorcoded overage indicators for a route, as shown in block 530 and 535. Inan embodiment, color or other indicators may be overlaid onto highwaymap 500. The coverage indicators may be for an entire route or may bemore granular to show coverage indicators for every mile, half mile, 5minute timeframe, or the like. The indicators may be a graphic, text, orsound (e.g., voice or a tone). In an embodiment, a user may be able toselect multiple data usage scenarios/options during the route fornavigation purposes. The multiple data usage scenarios (e.g., the topthree scenarios) may be based on information from the intelligentsubscriber profile. For example, the scenarios may be cloud Service 1,cloud Service 2, or Entertainment 1. The different scenarios may be anindicator of the type of protocol used, a descriptor of the end deviceaccessed, or the like.

In an embodiment, a predicted and/or a pre-constructed cell handoverpath for a WTRU may be based on the intelligent subscriber profilecombined with information from a navigation system. Analysis ofinformation associated with the expected route of a WTRU from thenavigation system and usage information from the intelligent subscriberprofile, for example, may allow the network to pre-construct when and towhat towers the WTRU should use. This pre-construction may allow forquicker and more efficient handover between cell towers as well as theselection of the network cell towers that are optimal for the WTRU whentraversing that route. For example, the selected cell towers may havehigher bandwidth capacity, provide better voice call quality, and/or mayhave less congestion or errors. In an embodiment, the selection of theradio towers used may be based on matching the predicted WTRU networkresources with an objective of the service provider to conserveresources (e.g., map to 3G resources instead of 4G resources based on aprediction for voice only).

FIG. 13 illustrates a non-limiting exemplary network configuration 600comprising a wide area wireless network domain 620 and an alternativenetwork domain 610. FIG. 14 with reference to FIG. 13 illustrates anon-limiting exemplary method 700 for switching between a wide areawireless network domain 620 and an alternative network domain 610. Atblock 705, a WTRU 605 may be connected to wide area wireless networkdomain 620. At block 710, WTRU 605 may enter into an alternative networkdomain 610 coverage area. At block 715, WTRU 605 may send an extensibleauthentication protocol (EAP) message to the alternative network domain610 (i.e., WiFi). At block 720, an alternative network domain server 612(e.g., a network management device) may receive the message and send aSend Authentication Information (SAI) to HLR/HSS 622 in request for anauthentication vector. At block 725, HLR/HSS 622 may reply with anauthentication vector alternative network domain server 612. At block730, alternative network domain server 622 may send a subsequentlocation updated (LU) to HLR/HSS 622 to request a subscriber profile forservice authorization. At block 735, HLR/HSS 622 may reply with thesubscriber profile. At block 740, alternative network domain server 612may extract subscriber account status from the received subscriberprofile in order to send permission right of usage of alternativenetwork domain 610 to WTRU 605. At block 745, the WTRU 605 may autoreconnect with the wide area wireless network 620 and auto disconnectfrom the alternative network domain 610 when out of range of thealternative network domain 610.

Method 700 may reduce the amount of signaling traffic when switchingbetween the alternative network domain and the wide area wirelessnetwork domain and reduce the HLR/HSS processing load. The wide areawireless network may instruct a connected WTRU to switch to analternative network domain based on congestion or an outage in the widearea wireless network. The wide area wireless network may also triggeran alert to WTRU when the congestion and/or outage is relieved. In anembodiment, wide area wireless network may instruct a connected WTRU toswitch to an alternative network domain based on predictive switching. AWTRU may have an associated intelligent subscriber profile. Although thewide area wireless network may not have congestion at a period of time,the wide area wireless network may proactively signal to the WTRU toswitch to an alternative network domain in consideration of a usageprediction from the intelligent subscriber profile.

When wireless networks become overly congested or encounters an outage,there is an opportunity to redirect the packet switched (PS) datatraffic to an alternative network domain. Disclosed herein is an“integrated” Authentication and Authorization method that can beperformed with reduced signaling (i.e., a single pass), so that thesignaling traffic may be reduced.

Communications between the AAA server with an alternative network domainand the HLR/HSS inside the LTE network may use the signaling channel(e.g., SS7, SIGTRAN, etc). Without an integrated AAA, a AAA server inthe alternative network domain may make multiple queries to the HLR/HSSin the mobility network domain. Furthermore when there is no integratedAAA, the AAA sever may validate subscriber identity and verify accountstatus each time the WTRU switches from the mobility domain to thealternative network domain.

In an embodiment, there may be a single HLR/HSS solution for integrated(“one-stop”) authentication and authorization. A server entitlementserver query may perform Authorization and then the HLR/HSS SAI Querymay be used perform authentication. The MIND and SAI query may avoidtypical HLR/HSS authorization which requires the Location Update Requestin order to return with the “entire” subscriber profile, which may beunnecessary and cumbersome. The method may comprise the client Box (ornetwork management device) issuing a Lightweight Directory AccessProtocol (LDAP) Authorization Request to reach the Subscriber ProfileRepository (SPR)/service entitlement server database in order toretrieve subscriber account status. And then, only if the subscriberaccount is active, the HLR/HSS authentication may be performed.

FIG. 15 illustrates a non-limiting exemplary network configuration 800according to one or more disclosed embodiments. Network managementdevice (NMD) 812 may optimally direct signaling traffic to anappropriate regional HLR/HSS. In an embodiment, the NMD 812 may extractHot Spot Location info based on RADIUS attributes (e.g., NAS identifier,NAS IP address, location name, location iD, user name, etc.) in order todirect the SAI traffic to the appropriate HLR, HSS 822, or the like. TheAAA device 814 may act as a nationwide backend server instead of aregional based server. In an embodiment, since the HLR/HSS 822 alreadymaintains multiple authentication vectors for each network as well as asubscriber profile, which may include account status, it may be moreefficient for HLR/HSS 822 to simply include a single status flag whichmay is a single indicator for the account status for the account overmultiple networks along with the authentication vector when replying tothe SAI request.

Embodiments disclosed herein may use a wide area wireless networkdomain, an alternative network domain interchangeably in itsimplementation. For example, the wireless navigation maps as discussedherein may display information based on wide area wireless networkdomains, alternative network domains, or both. In another example, atrigger to switch networks may come from the alternative network domainrather than the wide area wireless network domain.

While example embodiments for dynamic network domain interoperability,intelligent subscriber profiles, and the like have been described inconnection with various communications devices and computingdevices/processors, the underlying concepts can be applied to anycommunications or computing device, processor, or system capable ofimplementing the disclosed subject matter. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and apparatuses for dynamic network domain interoperability,intelligent subscriber profiles, or certain aspects or portions thereof,can take the form of program code (i.e., instructions) embodied intangible and/or non-transitory media, such as floppy diskettes, CD-ROMs,hard drives, or any other machine-readable storage medium, wherein, whenthe program code is loaded into and executed by a machine, such as acomputer, the machine becomes an apparatus for the disclosed subjectmatter. A computer-readable storage medium, as described herein is anarticle of manufacture, and should not to be construed as a transient orpropagating signal. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and combined with hardwareimplementations.

Methods and systems disclosed herein may also be practiced viacommunications embodied in the form of program code that is transmittedover some transmission medium, such as over electrical wiring orcabling, through fiber optics, or via any other form of transmission,wherein, when the program code is received, loaded into, and executed bya machine, such as an EPROM, a gate array, a programmable logic device(PLD), a client computer, or the like, the machine becomes an apparatusfor dynamic network domain interoperability, intelligent subscriberprofiles, and the like. When implemented on a general-purpose processor,the program code combines with the processor to provide a uniqueapparatus that operates to invoke the functionality of the disclosedsubject matter as described herein. Additionally, any storage techniquesused in connection with dynamic network domain interoperability,intelligent subscriber profiles, or other disclosed subject matter mayinvariably be a combination of hardware and software.

While the disclosed subject matter has been described in connection withthe various embodiments of the various figures, it is to be understoodthat other similar embodiments may be used or modifications andadditions may be made to the described embodiments for performing thesame function without deviating therefrom. For example, one skilled inthe art will recognize intelligent subscriber profiles as described inthe present application may apply to any environment, whether wired orwireless, and may be applied to any number of such devices connected viaa communications network and interacting across the network. Therefore,dynamic network domain interoperability, intelligent subscriberprofiles, or other disclosed subject matter should not be limited to anysingle embodiment, but rather should be construed in breadth and scopein accordance with the appended claims.

What is claimed is:
 1. A network device comprising: a processor; and amemory coupled to the processor, the memory having stored thereonexecutable instructions that when executed by the processor cause theprocessor to effectuate operations comprising: accessing informationassociated with a mobile device, the information associated with themobile device comprising a first data usage for a first data sessionassociated with the mobile device; predicting a second data usage for asecond data session associated with the mobile device based on ananalysis of the information associated with the mobile device; andproviding instructions to configure a network resource for the mobiledevice based on the predicted second data usage for the second datasession associated with the mobile device.
 2. The network device ofclaim 1, wherein the first data usage for the first data sessionassociated with the mobile device comprises at least one of: a time ofday a data session occurred, a type of a cloud service accessed, aduration of the data session, a volume of data accessed during the datasession, or a provider of the cloud service.
 3. The network device ofclaim 1, wherein the information associated with the mobile devicefurther comprises a user profile associated with the mobile device. 4.The network device of claim 3, wherein the user profile associated withthe mobile device comprises at least one of: a user preference for dataquality, a model number associated with the mobile device, a wirelesstechnology format capability associated with the mobile device,applications associated with the mobile device, a user preference forquality of service of a cloud service, or demographics of the user ofthe mobile device.
 5. The network device of claim 4, wherein thedemographics of the user of the mobile device comprises at least one of:age, home ownership, employment status, gender, height, weight,birthday, college education status, or income.
 6. The network device ofclaim 1, wherein the information associated with the mobile devicefurther comprises a rate plan associated with the mobile device.
 7. Thenetwork device of claim 6, wherein the rate plan associated with themobile device comprises at least one of: time based rate plan, bulk datausage based rate plan, or pay per use based rate plan.
 8. The networkdevice of claim 1, wherein the first data session is a type of cloudservice comprising at least one of: an infrastructure as a service,platform as a service, software as a service, storage as a service,security as a service, data as a service, test environment as a service,desktop as a service, or application program interface as a service. 9.The network device of claim 1, further comprising executableinstructions that cause the processor to effectuate operationscomprising: providing instructions to create an intelligent subscriberprofile, wherein the intelligent subscriber profile comprises a recordof the analysis that predicts the second data usage for the second datasession associated with the mobile device.
 10. The network device ofclaim 1, further comprising executable instructions that cause theprocessor to effectuate operations comprising: providing instructions todisplay an advertisement based on the predicted second data usage forthe second data session associated with the mobile device, wherein theadvertisement is displayed upon wake-up of the mobile device after atleast one of: wireless inactivity of the mobile device, deviceinactivity of the mobile device, or during the second data session. 11.The network device of claim 10, wherein the advertisement is a datausage plan that is subscribed to upon connecting to the second datasession.
 12. The network device of claim 10, further comprisingexecutable instructions that cause the processor to effectuateoperations comprising: providing instructions to the mobile device toaccess an alternate network domain at a particular timeframe based onthe predicted second data usage.
 13. A network device comprising: aprocessor; and a memory coupled to the processor, the memory havingstored thereon executable instructions that when executed by theprocessor cause the processor to effectuate operations comprising:accessing mapping data for a route to a destination; accessinginformation associated with a mobile device, the information associatedwith the mobile device comprising at least one of usage data of themobile device, a user profile associated with the mobile device, ordemographic data associated with a user of the mobile device; predictingcoverage for the mobile device along the route based on an analysis ofthe information associated with the mobile device and the mapping datafor the route; and providing instructions to display the route to thedestination along with an indicator of the predicted coverage for themobile device along the route.
 14. The network device of claim 13,further comprising executable instructions that cause the processor toeffectuate operations comprising: providing instructions to configure anetwork resource for the mobile device based on the route to thedestination.
 15. The network device of claim 13, wherein the indicatorcomprises at least one of text, a graphic, or sound.
 16. The networkdevice of claim 13, wherein the indicator characterizes at least aportion of the route.
 17. The network device of claim 13, furthercomprising executable instructions that cause the processor toeffectuate operations comprising: providing instructions to display anoption of the usage data to be analyzed for predicting the coverage forthe mobile device along the route.
 18. The network device of claim 13,further comprising executable instructions that cause the processor toeffectuate operations comprising: providing instructions to the mobiledevice to access an alternate network domain based on the predictedcoverage.
 19. A system comprising: a mobile device, the mobile devicecapable of accessing a wide area wireless network domain and alternatenetwork domain; and a network device comprising: a processor; and amemory coupled to the processor, the memory having stored thereonexecutable instructions that when executed by the processor cause theprocessor to effectuate operations comprising: accessing informationassociated with the mobile device, the information associated with themobile device comprising at least one of usage data of the mobiledevice, a user profile associated with the mobile device, or ademographic associated with a user of the mobile device; accessing acurrent state of a wide area wireless network; predicting the use of themobile device based on an analysis of the data associated with themobile device and the current state of the wide area wireless network;providing instructions to the mobile device to use the alternate networkdomain based on the predicted use of the mobile device.
 20. The systemof claim 19, wherein the network device authenticates the mobile devicefor the wide area wireless network and the alternate network domain.